home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 21
/
Cream of the Crop 21 (Terry Blount) (October 1996).iso
/
windows
/
pcp_w16.zip
/
INSTALL.TXT
next >
Wrap
Text File
|
1996-07-15
|
16KB
|
385 lines
Pine 3.95 RELEASE NOTES
Specific To PC-PINE
July 1996
Copyright 1989-1996 University of Washington.
Pine and Pico are trademarks of the University of Washington.
INTRODUCTION
The general release notes for this version of Pine are available via
the "R" command on the Main Menu. This file contains information that
is particular to PC-Pine. We assume that you are generally familiar
with Pine; if not, additional information resources include:
o The builtin context-sensitive Help screens in Pine.
o The comp.mail.pine newsgroup.
o The World-Wide-Web page at http://www.cac.washington.edu/pine
o The anonymous FTP archives at ftp://ftp.cac.washington.edu/pine
PC-Pine is available for the following environments:
o Windows: Windows95, NT 3.51
o Windows: version 3.X
o DOS: FTP Inc's PC-TCP
o DOS: Novell's LAN Workplace for DOS
o DOS: Sun's PC-NFS
o DOS: WATTCP/Packet Driver
The Winsock versions are not full Windows GUI applications; they have
basically the same user interface as the Unix and DOS versions of Pine
though modest GUI interaction is supported.
KNOWN BUGS
There are several bugs that we already know about:
o Under DOS, memory is tight. If you have run version 3.91, this
version requires about 15K more free memory to run (around 500K free).
Note, there are no memory restrictions under Windows 3.X, Windows95
or Windows NT.
o The Pipe command does not work properly under Windows95 and Windows NT.
o You cannot (yet) mount a Unix directory (via NFS or SMB) and successfully
share the same .newsrc file between your Unix and PC versions of Pine.
o The Winsock version is preliminary; we know that there are a number
of things that need to be done, however, your comments pro or con are
most welcome.
INSTALLATION INSTRUCTIONS
If you've made it this far, then you have already picked up a copy of
PC-Pine that is appropriate for your networking software and "unzipped"
the files in a directory (probably C:\Pine) on your PC's disk drive. In
the case of PC-Pine for Winsock, assuming you have Winsock/TCP/IP
networking software already installed, you can now use the Windows file
manager to create a new program item, or just use the "Run" option in the
program manager to start out. For the DOS versions, there are only a few
more things you have to do to get Pine rolling:
----------------------------------
Setting up the Networking Software
----------------------------------
We assume that your DOS networking software has been installed and
configured for regular use. If it has not, you must do that before
using Pine.
There are some additional steps that must be taken by users of
packet drivers, or older versions of FTP, Inc.'s PC/TCP. Those steps
are explained below.
PCs with a Packet Driver:
-------------------------
A) Edit the file WATTCP.CFG in the PC-Pine distribution to set
the PC's TCP/IP configuration. Simply edit the file to do this.
B) Every time Pine runs, it needs to be able to "see" the
WATTCP.CFG file you just configured above. To do that, you
must add an environment variable "WATTCP.CFG" to the file
AUTOEXEC.BAT. Here are the step-by-step instructions:
1) Edit the file C:\AUTOEXEC.BAT to add the following line -
set WATTCP.CFG=C:\PINE
2) Save the file and reboot your computer.
You will only have to do this packet driver specific configura-
tion work once.
X) ADDITIONAL NOTE: If you have a running version of NCSA telnet,
already installed on you PC, its "CONFIG.TEL" file can be used
instead of the WATTCP.CFG file. PC-Pine has a basic understanding
of the CONFIG.TEL format, and will recognize the "CONFIGTEL"
environment variable in the absence of a "WATTCP.CFG" environment
variable.
PCs with a PC/TCP Version Less than 2.2
---------------------------------------
A) You need a configuration file called "PCTCP.INI" in the Pine
directory. This can be created in one of two ways:
- If you have the program "Trans.exe" provided by FTP, Inc.,
then you can run this command:
trans ifcust0.sys > C:\Pine\pctcp.ini
- If you don't have "Trans.exe" or if that command does not
work for you, then create the file by hand. It needs to
contain just these two lines:
[pctcp ifcust 0]
ip-address=<your_pc's_ip_address>
Replace <your_pc's_ip_address> with the 4-section number
appropriate for your computer.
B) Every time Pine runs, it needs to be able to "see" the
PCTCP.INI file you just configured above. To do that, you
must add an environment variable "PCTCP.INI" to the file
AUTOEXEC.BAT. Here are the step-by-step instructions:
1) Edit the file C:\AUTOEXEC.BAT to add the following line -
set PCTCP=C:\PINE\PCTCP.INI
2) Save the file and reboot your computer.
You will only have to do this PC/TCP specific configuration
work once.
-----------------------------------
Essential Configuration Information
-----------------------------------
When you start PC-Pine for the first time, the program will prompt
you for certain information. That configuration data is written to
PC-Pine's configuration file (named PINERC in the directory you
unpacked pine in), so you will not have to enter it every time.
You should be prepared for the questions as PC-Pine can't really
proceed without the answers. If you make an error in any of these
entries, you can correct it in Pine's SETUP CONFIGURATION screen
(type "S" then "C" from the Main Menu).
Inbox
-----
When you read mail with PC-Pine, your mail is not delivered to your
PC directly. Rather, email is delivered to an IMAP server which
has been previously set up by your department/university/institution.
When you first start Pine, you need to specify where your INBOX
is. The syntax is this: {imap-server.domain}INBOX
User-id
-------
This is the user-id part of your email address.
Personal name
-------------
Your name as you want it to appear on outgoing email. You may have
spaces and punctuation in the name.
Host/domain
-----------
The "host" portion of your email address. This may be the full name
of the computer where your inbox resides or your departmental/
institutional domain if mail forwarding is set up. NOTE: You should
not put the name of your PC as the answer to this question -- your
PC is not where your INBOX resides.
SMTP server
-----------
Your PC does not have the software to interact with Internet email
directly. It must rely on an SMTP server to actually send your
message. You need to set this to the full name of the computer at
your site which provides SMTP service.
Example: Suppose the PC-Pine user is named "Joe User" and has
the login/email address of "juser". The individual is at the
University of Examples and takes advantage of the general
domain of "u.example.edu". He has set up his email so that
email is delivered to his inbox on the machine "imap.example.edu".
The University has set up an SMTP server on the machine named
"smtp-relay.example.edu". The PC running PC-Pine is on the campus
network and is called "pc-joe".
That person would answer PC Pine's configuration questions like this:
INBOX {imap.example.edu}INBOX
User-id juser
Personal Name Joe User
Host/domain u.example.edu
SMTP Server smtp-relay.example.edu
Email co